Fall protection equipment connection status and control

ABSTRACT

Techniques are described for monitoring and controlling fall protection equipment. For example, the techniques of this disclosure may be used to monitor the connection status of fall protection equipment, e.g., whether or not the fall protection equipment is connected to a support structure. The techniques of this disclosure may also be used to control the operation of the fall protection equipment based on the connection status.

TECHNICAL FIELD

This disclosure relates to safety equipment and, in particular, fallprotection equipment.

BACKGROUND

Fall protection equipment is important safety equipment for workersoperating at potentially harmful or even deadly heights. For example, tohelp ensure safety in the event of a fall, workers often wear safetyharnesses connected to support structures with fall protection equipmentsuch as lanyards, energy absorbers, self-retracting lanyards (SRLs),descenders, and the like. When a worker is connected to a supportstructure, the worker may be referred to as to being “tied off.” Inorder to maintain a safe working condition when working at height, aworker may maintain at least one connection to a support structure atall times.

Fall protection equipment may include a variety of components forconnecting a worker to a support structure (also referred to as ananchorage). For example, snap hooks and carabiners may have movablegates that allow a worker to connect to and disconnect from a supportstructure. As another example, a ladder safety sleeve may have a movablegate that allows the worker to connect to and disconnect from a climbingladder fall arrest system carrier e.g., flexible cable or rigid railsupport structure.

SUMMARY

In general, this disclosure describes techniques for monitoring andcontrolling fall protection equipment. For example, the techniques ofthis disclosure may be used to monitor the connection status of fallprotection equipment, e.g., whether or not the fall protection equipmentis connected to a support structure. The techniques of this disclosuremay also be used to control the operation of the fall protectionequipment based on the connection status. For example, aspects of thisdisclosure relate to determining that a particular article of fallprotection equipment is the only fall protection equipment connected toa support structure. Based on the determination, the techniques includeinitiating an alert and/or preventing the fall protection equipment frombeing disconnected from the support structure. In this way, thetechniques may help to ensure that worker maintains at least oneconnection to a support structure when working at height.

In one example, a method comprises determining that a first article offall protection equipment is connected to at least one supportstructure, the first article of fall protection equipment being includedin a set of fall protection equipment that comprises at least one secondarticle of fall protection equipment, determining that the first articleof fall protection equipment is the only article of fall protectionequipment in the set of fall protection equipment that is connected tothe at least one support structure, and performing, based on determiningthat the first article of fall protection equipment is the only articleof fall protection equipment that is connected to the at least onesupport structure, at least one operation.

In another example, a device comprises a memory configured to store datathat indicates whether a first article of fall protection equipment isconnected to at least one support structure. The device also comprisesone or more processors configured to communicate with the memory andconfigured to determine, based on the data, that the first article offall protection equipment is connected to the at least one supportstructure, the first article of fall protection equipment being includedin a set of fall protection equipment that comprises at least one secondarticle of fall protection equipment, determine that the first articleof fall protection equipment is the only article of fall protectionequipment in the set of fall protection equipment that is connected tothe at least one support structure, and perform, based on determiningthat the first article of fall protection equipment is the only articleof fall protection equipment that is connected to the at least onesupport structure, at least one operation.

In another example, a fall protection device comprising a body that atleast partially defines an area of attachment for attachment of the fallprotection device to a support structure, a movable gate connected tothe body and configured to move between an open position and a closedposition, wherein the open position provides access to the area ofattachment for attachment of the fall protection device to the supportstructure and the closed position prevents access to the area ofattachment, and a first sensor configured to generate data thatindicates whether the support structure is disposed within the area ofattachment.

In another example, a system comprises a set of fall protectionequipment comprising a first article of fall protection equipmentconfigured to be connected to at least one support structure and atleast one second article of fall protection equipment configured to beconnected to the at least one support structure. The system alsoincludes a hub comprising a communication unit configured to wirelesslycommunicate with the first article of fall protection equipment and theat least one second article of fall protection equipment, and one ormore processors configured to determine that the first article of fallprotection equipment is connected to the at least one support structure,determine that the first article of fall protection equipment is theonly article of fall protection equipment in the set of fall protectionequipment that is connected to the at least one support structure, andperform, based on determining that the first article of fall protectionequipment is the only article of fall protection equipment that isconnected to the at least one support structure, at least one operation.

The details of one or more examples of the disclosure are set forth inthe accompanying drawings and the description below. Other features,objects, and advantages of the disclosure will be apparent from thedescription and drawings, and from the claims.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram illustrating an example system in whichpersonal protection equipment (PPEs) having embedded sensors andcommunication capabilities are utilized within a number of workenvironments and are managed by a personal protection equipmentmanagement system in accordance with various techniques of thisdisclosure.

FIG. 2 is a block diagram illustrating an operating perspective of thepersonal protection equipment management system shown in FIG. 1.

FIG. 3 is a block diagram illustrating one example of a computing devicethat may be used to monitor and/or control fall protection equipment inaccordance with aspects of this disclosure.

FIG. 4 illustrates an example of a carabiner that is configured inaccordance with aspects of this disclosure.

FIG. 5 illustrates an example of a carrier sleeve that is configured inaccordance with aspects of this disclosure.

FIG. 6 illustrates another view of the ladder safety sleeve shown inFIG. 5.

FIG. 7 is a conceptual diagram illustrating an example of fallprotection equipment in communication with a wearable data hub, inaccordance with various aspects of this disclosure.

FIG. 8 is a flow diagram illustrating an example process for controllingthe operation of an article of fall protection equipment, according toaspects of this disclosure.

DETAILED DESCRIPTION

According to aspects of this disclosure, an article of fall protectionequipment may be configured to incorporate one or more electronicsensors for capturing data that is indicative of the operation of thefall protection equipment. Fall protection equipment may generally referto a device used to connect a user (e.g., a worker) to a supportstructure for the purpose of securing the user to the support structurein the event of a fall. Examples of fall protection equipment include avariety of carabiners (also referred to as “spring hooks” or “snaphooks”), shackles, carrier sleeves, or other devices that are capable ofconnecting a user to and disconnecting a user from the supportstructure. A particular example of a snap hook that may be adapted toincorporate certain techniques of this disclosure is the Saflok™ SnapHook manufactured by 3M Fall Protection Business. A particular exampleof a carrier sleeve may be adapted to incorporate certain techniques ofthis disclosure is the Lad-Saf™ X3 Detachable Carrier Sleevemanufactured by 3M Fall Protection Business. A support structure mayinclude an anchor, a lifeline, or another structure capable ofsupporting the weight of a user in the event of a fall.

In some examples, according to aspects of this disclosure, theelectronic sensors of the fall protection equipment may be configured tocapture data that is indicative of an operation or characteristic of thefall protection equipment. For example, the electronic sensors maycapture data that is indicative of a relative position of a component ofthe fall protection equipment (e.g., a position of a gate of a snaphook, carabiner, or carrier sleeve), data that is indicative of whethera support structure is disposed within an area of attachment for thefall protection equipment, or other operations or characteristics of thefall protection equipment. As described herein, an area of attachment offall protection equipment may generally refer to an area defined by oneor more components of the fall protection equipment that encompass thesupport structure. That is, when secured to a support structure, thearea of attachment is the area of the fall protection equipment in whichthe support structure is disposed. With respect to a carabiner as anexample, the area of attachment may be the interior area of thecarabiner defined by a body and a gate of the carabiner.

According to aspects of this disclosure, the fall protection equipmentand/or a computing device in communication with the fall protectionequipment may use the data from the sensors to determine state changesin a connection status of the fall protection equipment. A connectionstatus generally refers whether the fall protection equipment isconnected to a support structure.

In an example for purposes of illustration, an article of fallprotection equipment may include a carabiner having a gate that opensand closes to allow the carabiner to be connected to a supportstructure. According to aspects of this disclosure, in this particularexample, electronic sensors may be configured to capture data that isindicative of a relative position of the gate and data that isindicative of whether a support structure is disposed within thecarabiner. The carabiner (and/or a computing device in communicationwith the carabiner) may determine that the carabiner has been connectedto a support structure based on data that indicates that the gate hasbeen opened, that a support structure is disposed within the carabiner,and that the gate has been closed.

In some instances, the techniques of this disclosure may also be used tocontrol the operation of the fall protection equipment based on aconnection status. For example, in order to maintain a safe workingcondition when working at height, a worker may maintain at least oneconnection to a support structure throughout the time that the worker isworking at height. Aspects of this disclosure relate to determining thata particular article of fall protection equipment is the only fallprotection equipment connected to a support structure. Based on thedetermination, the techniques include initiating an alert and/orpreventing the fall protection equipment from being disconnected fromthe support structure, e.g., by actuating a lock or other device thathelps to prevent the fall protection equipment from being disconnectedfrom the support structure. In this way, the techniques may help toensure that worker maintains at least one connection to a supportstructure when working at height.

FIG. 1 is a block diagram illustrating an example computing system 2that includes a personal protection equipment management system (PPEMS)6 for managing personal protection equipment. As described herein, PPEMSallows authorized users to perform preventive occupational health andsafety actions and manage inspections and maintenance of safetyprotective equipment. By interacting with PPEMS 6, safety professionalscan, for example, manage area inspections, worker inspections, workerhealth and safety compliance training.

In general, PPEMS 6 provides data acquisition, monitoring, activitylogging, reporting, predictive analytics and alert generation. Forexample, PPEMS 6 includes an underlying analytics and safety eventprediction engine and alerting system in accordance with variousexamples described herein. As further described below, PPEMS 6 providesan integrated suite of personal safety protection equipment managementtools and implements various techniques of this disclosure. That is,PPEMS 6 provides an integrated, end-to-end system for managing personalprotection equipment, e.g., safety equipment, used by workers 8 withinone or more physical environments 10, which may be construction sites,mining or manufacturing sites or any physical environment. Thetechniques of this disclosure may be realized within various parts ofcomputing environment 2.

As shown in the example of FIG. 1, system 2 represents a computingenvironment in which a computing device within of a plurality ofphysical environments 8A, 8B (collectively, environments 8)electronically communicate with PPEMS 6 via one or more computernetworks 4. Each of physical environment 8 represents a physicalenvironment, such as a work environment, in which one or moreindividuals, such as workers 10, utilize personal protection equipmentwhile engaging in tasks or activities within the respective environment.

In this example, environment 8A is shown as generally as having workers10, while environment 8B is shown in expanded form to provide a moredetailed example. In the example of FIG. 1, a plurality of workers10A-10N are shown as utilizing respective fall protection equipment11A-11N (collectively, fall protection equipment 11), which are shown inthis example as a variety of carabiners, carrier sleeves, andself-retracting lanyards (SRLs), attached to safety support structure12.

As further described herein, each of fall protection equipment 11includes embedded sensors or monitoring devices and processingelectronics configured to capture data in real-time as a user (e.g.,worker) engages in activities while wearing the fall protectionequipment. For example, as described in greater detail with respect tothe example shown in FIG. 3, fall protection equipment 11 may include avariety of electronic sensors such as one or more sensors configured tosense a characteristic associated with a connection (referred to asconnection sensors) and one or more usage and environment sensors formeasuring operations of fall to protection equipment 11. In addition,each of fall protection equipment 11 may include one or more outputdevices for outputting data that is indicative of operation of fallprotection equipment 11 and/or generating and outputting communicationsto the respective worker 10. For example, fall protection equipment 11may include one or more devices to generate audible feedback (e.g., oneor more speakers), visual feedback (e.g., one or more displays, lightemitting diodes (LEDs) or the like), or tactile feedback (e.g., a devicethat vibrates or provides other haptic feedback).

In general, each of environments 8 include computing facilities (e.g., alocal area network) by which fall protection equipment 11 is able tocommunicate with PPEMS 6. For examples, environments 8 may be configuredwith wireless technology, such as 802.11 wireless networks, 802.15ZigBee networks, and the like. In the example of FIG. 1, environment 8Bincludes a local network 7 that provides a packet-based transport mediumfor communicating with PPEMS 6 via network 4. In addition, environment8B includes a plurality of wireless access points 19A, 19B that may begeographically distributed throughout the environment to provide supportfor wireless communications throughout the work environment.

Each of fall protection equipment 11 is configured to communicate data,such as sensed motions, events and conditions, via wirelesscommunications, such as via 802.11 WiFi protocols, Bluetooth protocol orthe like. Fall protection equipment 11 may, for example, communicatedirectly with a wireless access point 19. As another example, eachworker 10 may be equipped with a respective one of wearablecommunication hubs 14A-14M that enable and facilitate communicationbetween fall protection equipment 11 and PPEMS 6. For examples, fallprotection equipment 11 as well as other PPEs for the respective worker10 may communicate with a respective communication hub 14 via Bluetoothor other short range protocol, and the communication hubs maycommunicate with PPEMs 6 via wireless communications processed bywireless access points 19. Although shown as wearable devices, hubs 14may be implemented as stand-alone devices deployed within environment8B.

In some instances, each of hubs 14 may operate as a wireless device forfall protection equipment 11 relaying communications to and from fallprotection equipment 11, and may be capable of buffering usage data incase communication is lost with PPEMS 6. Moreover, each of hubs 14 isprogrammable via PPEMS 6 so that local alert rules may be installed andexecuted without requiring a connection to the cloud. As such, each ofhubs 14 provides a relay of streams of usage data from fall protectionequipment 11 and/or other PPEs within the respective environment, andprovides a local computing environment for localized alerting based onstreams of events in the event communication with PPEMS 6 is lost.

As shown in the example of FIG. 1, an environment, such as environment8B, may also one or more wireless-enabled beacons, such as beacons17A-17C, that provide accurate location information within the workenvironment. For example, beacons 17A-17C may be GPS-enabled such that acontroller within the respective beacon may be able to preciselydetermine the position of the respective beacon. Based on wirelesscommunications with one or more of beacons 17, a given article of fallprotection equipment 11 or communication hub 14 worn by a worker 10 isconfigured to determine the location of the worker within workenvironment 8B. In this way, event data reported to PPEMS 6 may bestamped with positional information to aid analysis, reporting andanalytics performed by the PPEMS.

In addition, an environment, such as environment 8B, may also one ormore wireless-enabled sensing stations, such as sensing stations 21A,21B. Each sensing station 21 includes one or more sensors and acontroller configured to output data indicative of sensed environmentalconditions. Moreover, sensing stations 21 may be positioned withinrespective geographic regions of environment 8B or otherwise interactwith beacons 17 to determine respective positions and include suchpositional information when reporting environmental data to PPEMS 6.

As such, PPEMS 6 may configured to correlate the senses environmentalconditions with the particular regions and, therefore, may utilize thecaptured environmental data when processing event data received fromfall protection equipment 11. For example, PPEMS 6 may utilize theenvironmental data to aid generating alerts or other instructions forfall protection equipment 11 and for performing predictive analytics,such as determining any correlations between certain environmentalconditions (e.g., wind speed, heat, humidity, visibility) with abnormalworker behavior or increased safety events. As such, PPEMS 6 may utilizecurrent environmental conditions to aid prediction and avoidance ofimminent safety events. Example environmental conditions that may besensed by sensing devices 21 include but are not limited to temperature,humidity, presence of gas, pressure, visibility, wind speed and thelike.

In example implementations, an environment, such as environment 8B, mayalso include one or more safety stations 15 distributed throughout theenvironment to provide viewing stations for accessing PPEMs 6. Safetystations 15 may allow one of workers 10 to check out fall protectionequipment 11 and/or other safety equipment, verify that safety equipmentis appropriate for a particular one of environments 8, and/or exchangedata. For example, safety stations 15 may transmit alert rules, softwareupdates, or firmware updates to fall protection equipment 11 or otherequipment. Safety stations 15 may also receive data cached on fallprotection equipment 11, hubs 14, and/or other safety equipment. Thatis, while fall protection equipment 11 (and/or data hubs 14) maytypically transmit usage data from sensors of fall protection equipment11 to network 4, in some instances, fall protection equipment 11 (and/ordata hubs 14) may not have connectivity to network 4. In such instances,fall protection equipment 11 (and/or data hubs 14) may store usage datalocally and transmit the usage data to safety stations 15 upon being inproximity with safety stations 15. Safety stations 15 may then uploadthe data from fall protection equipment 11 and connect to network 4.

In addition, each of environments 8 include computing facilities thatprovide an operating environment for end-user computing devices 16 forinteracting with PPEMS 6 via network 4. For example, each ofenvironments 8 typically includes one or more safety managersresponsible for overseeing safety compliance within the environment. Ingeneral, each user 20 interacts with computing devices 16 to accessPPEMS 6. Each of environments 8 may include systems. Similarly, remoteusers may use computing devices 18 to interact with PPEMS via network 4.For purposes of example, the end-user computing devices 16 may belaptops, desktop computers, mobile devices such as tablets or so-calledsmart phones and the like.

Users 20, 24 interact with PPEMS 6 to control and actively manage manyaspects of safely equipment utilized by workers 10, such as accessingand viewing usage records, analytics and reporting. For example, users20, 24 may review usage information acquired and stored by PPEMS 6,where the usage information may include data specifying starting andending times over a time duration (e.g., a day, a week, or the like),data collected during particular events, such as detected falls, senseddata acquired from the user, environment data, and the like. Inaddition, users 20, 24 may interact with PPEMS 6 to perform assettracking and to schedule maintenance events for individual pieces ofsafety equipment, e.g., fall protection equipment 11, to ensurecompliance with any procedures or regulations. PPEMS 6 may allow users20, 24 to create and complete digital checklists with respect to themaintenance procedures and to synchronize any results of the proceduresfrom computing devices 16, 18 to PPEMS 6.

Further, as described herein, PPEMS 6 integrates an event processingplatform configured to process thousand or even millions of concurrentstreams of events from digitally enabled PPEs, such as fall protectionequipment 11. An underlying analytics engine of PPEMS 6 may applyhistorical data and models to the inbound streams to compute assertions,such as identified anomalies or predicted occurrences of safety eventsbased on conditions or behavior patterns of workers 10. Further, PPEMS 6may provide real-time alerting and reporting to notify workers 10 and/orusers 20, 24 of any predicted events, anomalies, trends, and the like.

The analytics engine of PPEMS 6 may, in some examples, apply analyticsto identify relationships or correlations between sensed worker data,environmental conditions, geographic regions and other factors andanalyze the impact on safety events. PPEMS 6 may determine, based on thedata acquired across populations of workers 10, which particularactivities, possibly within certain geographic region, lead to, or arepredicted to lead to, unusually high occurrences of safety events.

In this way, PPEMS 6 integrates comprehensive tools for managingpersonal protection equipment with an underlying analytics engine andcommunication system to provide data acquisition, monitoring, activitylogging, reporting, behavior analytics and alert generation. Moreover,PPEMS 6 provides a communication system for operation and utilization byand between the various elements of system 2. Users 20, 24 may accessPPEMS to view results on any analytics performed by PPEMS 6 on dataacquired from workers 10. In some examples, PPEMS 6 may present aweb-based interface via a web server (e.g., an HTTP server) orclient-side applications may be deployed for devices of computingdevices 16, 18 used by users 20, 24, such as desktop computers, laptopcomputers, mobile devices such as smartphones and tablets, or the like.

In some examples, PPEMS 6 may provide a database query engine fordirectly querying PPEMS 6 to view acquired safety information,compliance information and any results of the analytic engine, e.g., bythe way of dashboards, alert notifications, reports and the like. Thatis, users 24, 26, or software executing on computing devices 16, 18, maysubmit queries to PPEMS 6 and receive data corresponding to the queriesfor presentation in the form of one or more reports or dashboards. Suchdashboards may provide various insights regarding system 2, such asbaseline (“normal”) operation across worker populations, identificationsof any anomalous workers engaging in abnormal activities that maypotentially expose the worker to risks, identifications of anygeographic regions within environments 2 for which unusually anomalous(e.g., high) safety events have been or are predicted to occur,identifications of any of environments 2 exhibiting anomalousoccurrences of safety events relative to other environments, and thelike.

PPEMS 6 may simplify workflows for individuals charged with monitoringand ensure safety compliance for an entity or environment. That is, thetechniques of this disclosure may enable active safety management andallow an organization to take preventative or correction actions withrespect to certain regions within environments 8, particular articles offall protection equipment 11 or individual workers 10, define and mayfurther allow the entity to implement workflow procedures that aredata-driven by an underlying analytical engine.

As one example, the underlying analytical engine of PPEMS 6 may beconfigured to compute and present customer-defined metrics for workerpopulations within a given environment 8 or across multiple environmentsfor an organization as a whole. For example, PPEMS 6 may be configuredto acquire data and provide aggregated performance metrics and predictedbehavior analytics across a worker population (e.g., across workers 10of either or both of environments 8A, 8B). Furthermore, users 20, 24 mayset benchmarks for occurrence of any safety incidences, and PPEMS 6 maytrack actual performance metrics relative to the benchmarks forindividuals or defined worker populations.

As another example, PPEMS 6 may further trigger an alert if certaincombinations of conditions are present, e.g., to accelerate examinationor service of a safety equipment, such as one of fall protectionequipment 11. In this manner, PPEMS 6 may identify individual articlesof fall protection equipment 11 or workers 10 for which the metrics donot meet the benchmarks and prompt the users to intervene and/or performprocedures to improve the metrics relative to the benchmarks, therebyensuring compliance and actively managing safety for workers 10.

FIG. 2 is a block diagram providing an operating perspective of PPEMS 6when hosted as cloud-based platform capable of supporting multiple,distinct work environments 8 having an overall population of workers 10that have a variety of communication enabled personal protectionequipment (PPE), such as fall protection equipment 11, respirators 13,safety helmets or other safety equipment. In the example of FIG. 2, thecomponents of PPEMS 6 are arranged according to multiple logical layersthat implement the techniques of the disclosure. Each layer may beimplemented by one or more modules comprised of hardware, software, or acombination of hardware and software.

In FIG. 2, personal protection equipment (PPEs) 62, such as fallprotection equipment 11, respirators 13 and/or other equipment, eitherdirectly or by way of hubs 14, as well as computing devices 60, operateas clients 63 that communicate with PPEMS 6 via interface layer 64.Computing devices 60 typically execute client software applications,such as desktop applications, mobile application, and web applications.Computing devices 60 may represent any of computing devices 16, 18 ofFIG. 1. Examples of computing devices 60 may include, but are notlimited to a portable or mobile computing device (e.g., smartphone,wearable computing device, tablet), laptop computers, desktop computers,smart television platforms, and servers, to name only a few examples.

As further described in this disclosure, PPEs 62 communicate with PPEMS6 (directly or via hubs 14) to provide streams of data acquired fromembedded sensors and other monitoring circuitry and receive from PPEMS 6alerts, configuration and other communications. Client applicationsexecuting on computing devices 60 may communicate with PPEMS 6 to sendand receive information that is retrieved, stored, generated, and/orotherwise processed by services 68. For instance, the clientapplications may request and edit safety event information includinganalytical data stored at and/or managed by PPEMS 6. In some examples,client applications 61 may request and display aggregate safety eventinformation that summarizes or otherwise aggregates numerous individualinstances of safety events and corresponding data acquired from PPEs 62and or generated by PPEMS 6. The client applications may interact withPPEMS 6 to query for analytics information about past and predictedsafety events, behavior trends of workers 10, to name only a fewexamples. In some examples, the client applications may output fordisplay information received from PPEMS 6 to visualize such informationfor users of clients 63. As further illustrated and described in below,PPEMS 6 may provide information to the client applications, which theclient applications output for display in user interfaces.

Clients applications executing on computing devices 60 may beimplemented for different platforms but include similar or the samefunctionality. For instance, a client application may be a desktopapplication compiled to run on a desktop operating system, such asMicrosoft Windows, Apple OS X, or Linux, to name only a few examples. Asanother example, a client application may be a mobile applicationcompiled to run on a mobile operating system, such as Google Android,Apple iOS, Microsoft Windows Mobile, or BlackBerry OS to name only a fewexamples. As another example, a client application may be a webapplication such as a web browser that displays web pages received fromPPEMS 6.

In the example of a web application, PPEMS 6 may receive requests fromthe web application (e.g., the web browser), process the requests, andsend one or more responses back to the web application. In this way, thecollection of web pages, the client-side processing web application, andthe server-side processing performed by PPEMS 6 collectively providesthe functionality to perform techniques of this disclosure. In this way,client applications use various services of PPEMS 6 in accordance withtechniques of this disclosure, and the applications may operate withinvarious different computing environment (e.g., embedded circuitry orprocessor of a PPE, a desktop operating system, mobile operating system,or web browser, to name only a few examples).

As shown in FIG. 2, PPEMS 6 includes an interface layer 64 thatrepresents a set of application programming interfaces (API) or protocolinterface presented and supported by PPEMS 6. Interface layer 64initially receives messages from any of clients 63 for furtherprocessing at PPEMS 6. Interface layer 64 may therefore provide one ormore interfaces that are available to client applications executing onclients 63. In some examples, the interfaces may be applicationprogramming interfaces (APIs) that are accessible over a network.Interface layer 64 may be implemented with one or more web servers. Theone or more web servers may receive incoming requests, process and/orforward information from the requests to services 68, and provide one ormore responses, based on information received from services 68, to theclient application that initially sent the request. In some examples,the one or more web servers that implement interface layer 64 mayinclude a runtime environment to deploy program logic that provides theone or more interfaces. As further described below, each service mayprovide a group of one or more interfaces that are accessible viainterface layer 64.

In some examples, interface layer 64 may provide Representational StateTransfer (RESTful) interfaces that use HTTP methods to interact withservices and manipulate resources of PPEMS 6. In such examples, services68 may generate JavaScript Object Notation (JSON) messages thatinterface layer 64 sends back to the client application 61 thatsubmitted the initial request. In some examples, interface layer 64provides web services using Simple Object Access Protocol (SOAP) toprocess requests from client applications 61. In still other examples,interface layer 64 may use Remote Procedure Calls (RPC) to processrequests from clients 63. Upon receiving a request from a clientapplication to use one or more services 68, interface layer 64 sends theinformation to application layer 66, which includes services 68.

As shown in FIG. 2, PPEMS 6 also includes an application layer 66 thatrepresents a collection of services for implementing much of theunderlying operations of PPEMS 6. Application layer 66 receivesinformation included in requests received from client applications 61and further processes the information according to one or more ofservices 68 invoked by the requests. Application layer 66 may beimplemented as one or more discrete software services executing on oneor more application servers, e.g., physical or virtual machines. Thatis, the application servers provide runtime environments for executionof services 68. In some examples, the functionality interface layer 64as described above and the functionality of application layer 66 may beimplemented at the same server.

Application layer 66 may include one or more separate software services68, e.g., processes that communicate, e.g., via a logical service bus 70as one example. Service bus 70 generally represents logicalinterconnections or set of interfaces that allows different services tosend messages to other services, such as by a publish/subscriptioncommunication model. For instance, each of services 68 may subscribe tospecific types of messages based on criteria set for the respectiveservice.

When a service publishes a message of a particular type on service bus70, other services that subscribe to messages of that type will receivethe message. In this way, each of services 68 may communicateinformation to one another. As another example, services 68 maycommunicate in point-to-point fashion using sockets or othercommunication mechanism. In still other examples, a pipeline systemarchitecture could be used to enforce a workflow and logical processingof data messages as they are process by the software system services.Before describing the functionality of each of services 68, the layersare briefly described herein.

Data layer 72 of PPEMS 6 represents a data repository that providespersistence for information in PPEMS 6 using one or more datarepositories 74. A data repository, generally, may be any data structureor software that stores and/or manages data. Examples of datarepositories include but are not limited to relational databases,multi-dimensional databases, maps, and hash tables, to name only a fewexamples. Data layer 72 may be implemented using Relational DatabaseManagement System (RDBMS) software to manage information in datarepositories 74. The RDBMS software may manage one or more datarepositories 74, which may be accessed using Structured Query Language(SQL). Information in the one or more databases may be stored,retrieved, and modified using the RDBMS software. In some examples, datalayer 72 may be implemented using an Object Database Management System(ODBMS), Online Analytical Processing (OLAP) database or other suitabledata management system.

As shown in FIG. 2, each of services 68A-68H (“services 68”) isimplemented in a modular form within PPEMS 6. Although shown as separatemodules for each service, in some examples the functionality of two ormore services may be combined into a single module or component. Each ofservices 68 may be implemented in software, hardware, or a combinationof hardware and software. Moreover, services 68 may be implemented asstandalone devices, separate virtual machines or containers, processes,threads or software instructions generally for execution on one or morephysical processors.

In some examples, one or more of services 68 may each provide one ormore interfaces that are exposed through interface layer 64.Accordingly, client applications of computing devices 60 may call one ormore interfaces of one or more of services 68 to perform techniques ofthis disclosure.

In accordance with techniques of the disclosure, services 68 may includean event processing platform including an event endpoint frontend 68A,event selector 68B, event processor 68C and high priority (HP) eventprocessor 68D. Event endpoint frontend 68A operates as a front-endinterface for receiving and sending communications to PPEs 62 and hubs14. In other words, event endpoint frontend 68A operates to as afront-line interface to safety equipment deployed within environments 8and utilized by workers 10.

In some instances, event endpoint frontend 68A may be implemented as aplurality of tasks or jobs spawned to receive individual inboundcommunications of event streams 69 from the PPEs 62 carrying data sensedand captured by the safety equipment. When receiving event streams 69,for example, event endpoint frontend 68A may spawn tasks to quicklyenqueue an inbound communication, referred to as an event, and close thecommunication session, thereby providing high-speed processing andscalability. Each incoming communication may, for example, carry datarecently captured data representing sensed conditions, motions,temperatures, actions or other data, generally referred to as events.Communications exchanged between the event endpoint frontend 68A and thePPEs may be real-time or pseudo real-time depending on communicationdelays and continuity.

Event selector 68B operates on the stream of events 69 received fromPPEs 62 and/or hubs 14 via frontend 68A and determines, based on rulesor classifications, priorities associated with the incoming events.Based on the priorities, event selector 68B enqueues the events forsubsequent processing by event processor 68C or high priority (HP) eventprocessor 68D. Additional computational resources and objects may bededicated to HP event processor 68D so as to ensure responsiveness tocritical events, such as incorrect usage of PPEs, use of incorrectfilters and/or respirators based on geographic locations and conditions,failure to properly secure fall protection equipment 11 and the like.Responsive to processing high priority events, HP event processor 68Dmay immediately invoke notification service 68E to generate alerts,instructions, warnings or other similar messages to be output to fallprotection equipment 11, hubs 14 and/or remote users 20, 24. Events notclassified as high priority are consumed and processed by eventprocessor 68C.

In general, event processor 68C or high priority (HP) event processor68D operate on the incoming streams of events to update event data 74Awithin data repositories 74. In general, event data 74A may include allor a subset of usage data obtained from PPEs 62. For example, in someinstances, event data 74A may include entire streams of samples of dataobtained from electronic sensors of PPEs 62. In other instances, eventdata 74A may include a subset of such data, e.g., associated with aparticular time period or activity of PPEs 62.

Event processors 68C, 68D may create, read, update, and delete eventinformation stored in event data 74A. Event information for may bestored in a respective database record as a structure that includesname/value pairs of information, such as data tables specified inrow/column format. For instance, a name (e.g., column) may be “workerID” and a value may be an employee identification number. An eventrecord may include information such as, but not limited to: workeridentification, PPE identification, acquisition timestamp(s) and dataindicative of one or more sensed parameters.

In addition, event selector 68B directs the incoming stream of events tostream analytics service 68F, which represents an example of ananalytics engine configured to perform in depth processing of theincoming stream of events to perform real-time analytics. Streamanalytics service 68F may, for example, be configured to process andcompare multiple streams of event data 74A with historical data andmodels 74B in real-time as event data 74A is received. In this way,stream analytic service 68D may be configured to detect anomalies,transform incoming event data values, trigger alerts upon detectingsafety concerns based on conditions or worker behaviors.

Historical data and models 74B may include, for example, specifiedsafety rules, business rules and the like. In this way, historical dataand models 74B may characterize activity of a user of fall protectionequipment 11, e.g., as conforming to the safety rules, business rules,and the like. In addition, stream analytic service 68D may generateoutput for communicating to PPPEs 62 by notification service 68F orcomputing devices 60 by way of record management and reporting service68D.

Analytics service 68F may process inbound streams of events, potentiallyhundreds or thousands of streams of events, from enabled safety PPEs 62utilized by workers 10 within environments 8 to apply historical dataand models 74B to compute assertions, such as identified anomalies orpredicted occurrences of imminent safety events based on conditions orbehavior patterns of the workers. Analytics service may 68D publish theassertions to notification service 68F and/or record management byservice bus 70 for output to any of clients 63.

In this way, analytics service 68F may configured as an active safetymanagement system that predicts imminent safety concerns and providesreal-time alerting and reporting. In addition, analytics service 68F maybe a decision support system that provides techniques for processinginbound streams of event data to generate assertions in the form ofstatistics, conclusions, and/or recommendations on an aggregate orindividualized worker and/or PPE basis for enterprises, safety officersand other remote users. For instance, analytics service 68F may applyhistorical data and models 74B to determine, for a particular worker,the likelihood that a safety event is imminent for the worker based ondetected behavior or activity patterns, environmental conditions andgeographic locations.

In some examples, analytics service 68F may generate user interfacesbased on processing information stored by PPEMS 6 to provide actionableinformation to any of clients 63. For example, analytics service 68F maygenerate dashboards, alert notifications, reports and the like foroutput at any of clients 63. Such information may provide variousinsights regarding baseline (“normal”) operation across workerpopulations, identifications of any anomalous workers engaging inabnormal activities that may potentially expose the worker to risks,identifications of any geographic regions within environments for whichunusually anomalous (e.g., high) safety events have been or arepredicted to occur, identifications of any of environments exhibitinganomalous occurrences of safety events relative to other environments,and the like.

Although other technologies can be used, in one example implementation,analytics service 68F utilizes machine learning when operating onstreams of safety events so as to perform real-time analytics. That is,analytics service 68F includes executable code generated by applicationof machine learning to training data of event streams and known safetyevents to detect patterns. The executable code may take the form ofsoftware instructions or rule sets and is generally referred to as amodel that can subsequently be applied to event streams 69 for detectingsimilar patterns and predicting upcoming events.

Analytics service 68F may, in some example, generate separate models fora particular worker, a particular population of workers, a particularenvironment, or combinations thereof. Analytics service 68F may updatethe models based on usage data received from PPEs 62. For example,analytics service 68F may update the models for a particular worker, aparticular population of workers, a particular environment, orcombinations thereof based on data received from PPEs 62.

Alternatively, or in addition, analytics service 68F may communicate allor portions of the generated code and/or the machine learning models tohubs 14 (or PPEs 62) for execution thereon so as to provide localalerting in near-real time to PPEs. Example machine learning techniquesthat may be employed to generate models 74B can include various learningstyles, such as supervised learning, unsupervised learning, andsemi-supervised learning. Example types of algorithms include Bayesianalgorithms, Clustering algorithms, decision-tree algorithms,regularization algorithms, regression algorithms, instance-basedalgorithms, artificial neural network algorithms, deep learningalgorithms, dimensionality reduction algorithms and the like. Variousexamples of specific algorithms include Bayesian Linear Regression,Boosted Decision Tree Regression, and Neural Network Regression, BackPropagation Neural Networks, the Apriori algorithm, K-Means Clustering,k-Nearest Neighbour (kNN), Learning Vector Quantization (LVQ),Self-Organizing Map (SOM), Locally Weighted Learning (LWL), RidgeRegression, Least Absolute Shrinkage and Selection Operator (LASSO),Elastic Net, and Least-Angle Regression (LARS), Principal ComponentAnalysis (PCA) and Principal Component Regression (PCR).

Record management and reporting service 68G processes and responds tomessages and queries received from computing devices 60 via interfacelayer 64. For example, record management and reporting service 68G mayreceive requests from client computing devices for event data related toindividual workers, populations or sample sets of workers, geographicregions of environments 8 or environments 8 as a whole, individual orgroups/types of PPEs 62. In response, record management and reportingservice 68G accesses event information based on the request. Uponretrieving the event data, record management and reporting service 68Gconstructs an output response to the client application that initiallyrequested the information.

As additional examples, record management and reporting service 68G mayreceive requests to find, analyze, and correlate PPE event information.For instance, record management and reporting service 68G may receive aquery request from a client application for event data 74A over ahistorical time frame, such as a user can view PPE event informationover a period of time and/or a computing device can analyze the PPEevent information over the period of time.

In example implementations, services 68 may also include securityservice 68H that authenticate and authorize users and requests withPPEMS 6. Specifically, security service 68H may receive authenticationrequests from client applications and/or other services 68 to accessdata in data layer 72 and/or perform processing in application layer 66.An authentication request may include credentials, such as a usernameand password. Security service 68H may query security data 74A todetermine whether the username and password combination is valid.Configuration data 74D may include security data in the form ofauthorization credentials, policies, and any other information forcontrolling access to PPEMS 6. As described above, security data 74A mayinclude authorization credentials, such as combinations of validusernames and passwords for authorized users of PPEMS 6. Othercredentials may include device identifiers or device profiles that areallowed to access PPEMS 6.

Security service 68H may provide audit and logging functionality foroperations performed at PPEMS 6. For instance, security service 68H maylog operations performed by services 68 and/or data accessed by services68 in data layer 72. Security service 68H may store audit informationsuch as logged operations, accessed data, and rule processing results inaudit data 74C. In some examples, security service 68H may generateevents in response to one or more rules being satisfied. Securityservice 68H may store data indicating the events in audit data 74C.

PPEMS 6 may include self-check component 681, self-check criteria 74Eand work relation data 74F. Self-check criteria 74E may include one ormore self-check criterion. Work relation data 74F may include mappingsbetween data that corresponds to PPE, workers, and work environments.Work relation data 74F may be any suitable datastore for storing,retrieving, updating and deleting data. Work relation data store 74F maystore a mapping between the unique identifier of worker 10A and a uniquedevice identifier of data hub 14A. Work relation data store 74F may alsomap a worker to an environment. In the example of FIG. 2, self-checkcomponent 681 may receive or otherwise determine data from work relationdata 74F for data hub 14A, worker 10A, and/or PPE associated with orassigned to worker 10A. Based on this data, self-check component 681 mayselect one or more self-check criteria from self-check criteria 74E.Self-check component 681 may send the self-check criteria to data hub14A.

FIG. 3 illustrates an example of a computing device that may beincorporated in an article of fall protection equipment 11. In theillustrated example, computing device 98 includes processors 100, memory102, communication unit 104, one or more connection sensors 106, fallprotection unit 108, one or more usage and environment sensors 110, andoutput unit 112. It should be understood that the architecture andarrangement of computing device 98 illustrated in FIG. 3 is shown forexemplary purposes only. In other examples, computing device 98incorporated in an article of fall protection equipment may beconfigured in a variety of other ways having additional, fewer, oralternative components than those shown in FIG. 3. For example, asdescribed in greater detail below, computing device 98 may be configuredto include only a subset of components, such as communication unit 104and connection sensors 106 and may offload certain processing functionsto anther device, such as one of hubs 14.

In general, computing device 98 may include a plurality of sensors thatmay capture real-time data regarding operation of fall protectionequipment 11 and/or an environment in which fall protection equipment 11is used. Such data may be referred to herein as usage data. Processors100, in one example, are configured to implement functionality and/orprocess instructions for execution within computing device 98. Forexample, processors 100 may be capable of processing instructions storedby memory 102. Processors 100 may include, for example, microprocessors,digital signal processors (DSPs), application specific integratedcircuits (ASICs), field-programmable gate array (FPGAs), or equivalentdiscrete or integrated logic circuitry.

Memory 102 may include a computer-readable storage medium orcomputer-readable storage device. In some examples, memory 102 mayinclude one or more of a short-term memory or a long-term memory. Memory102 may include, for example, random access memories (RAM), dynamicrandom access memories (DRAM), static random access memories (SRAM),magnetic hard discs, optical discs, flash memories, or forms ofelectrically programmable memories (EPROM) or electrically erasable andprogrammable memories (EEPROM).

In some examples, memory 102 may store an operating system (not shown)or other application that controls the operation of components ofcomputing device 98. For example, the operating system may facilitatethe communication of data from electronic sensors (e.g., connectionsensors 106) to communication unit 104. In some examples, memory 102 isused to store program instructions for execution by processors 100.Memory 102 may also be configured to store information within computingdevice 98 during operation.

Computing device 98 may use communication unit 104 to communicate withexternal devices via one or more wired or wireless connections.Communication unit 104 may include various mixers, filters, amplifiersand other components designed for signal modulation, as well as one ormore antennas and/or other components designed for transmitting andreceiving data. Communication unit 104 may send and receive data toother computing devices using any one or more suitable datacommunication techniques. Examples of such communication techniques mayinclude TCP/IP, Ethernet, Wi-Fi, Bluetooth, 4G, LTE, to name only a fewexamples. In some instances, communication unit 104 may operate inaccordance with the Bluetooth Low Energy (BLU) protocol.

Connection sensors 106 may include a wide variety of sensorsincorporated in fall protection equipment 11 and configured to generateoutput data indicative of an operation of fall protection equipment 11or a characteristic of fall protection equipment 11. For example, theconnection sensors 106 may capture data that is indicative of a relativeposition of a component of fall protection equipment 11 or data that isindicative of whether a support structure is disposed within an area ofattachment for fall protection equipment 11. Example connection sensors106 include one or more switches, hall effect sensors, magnetic sensors,optical sensors, ultrasonic sensors, photoelectric sensors, rotaryencoders, accelerometers, or the like. Particular examples of connectionsensors 106 are described with respect to the examples of FIGS. 4 and 5below.

Fall protection unit 108 may include any combination of hardware andsoftware (e.g., executable by processors 100) to control the operationof a lock 109 (as described in greater detail, for example, with respectto FIGS. 4-6 below) incorporated in fall protection equipment 11. Asdescribed herein, a lock may include any device capable of impeding orpreventing fall protection equipment 11 from being disconnected from asupport structure. As merely one example and as described in greaterdetail with respect to the example shown in FIG. 6, lock 109 may includea solenoid that extends to prevent the movement of one or morecomponents of fall to protection equipment 11 to impede or prevent fallprotection equipment from being disconnected from a support structure.Fall protection unit 108 may control the operation of lock 109 and/orfeedback component 113, e.g., based on data from connection sensors 106.

Usage and environment sensors 110 may include a wide variety of sensorsthat capture data indicative of manner in which of fall protectionequipment 11 is being used or an environment in which fall protectionequipment 11 is disposed. For example, usage and environment sensors 110may include accelerometers, location sensors, altimeters, or the like.In this example, an accelerometer may be configured to generate dataindicative of an acceleration of fall protection equipment 11 withrespect to gravity. An accelerometer may be configured as a single- ormulti-axis accelerometer to determine a magnitude and direction ofacceleration, e.g., as a vector quantity, and may be used to determineorientation, coordinate acceleration, vibration, shock, and/or falling.A location sensor may be configured to generate data indicative of alocation of fall protection equipment 11 in one of environments 8. Thelocation sensor may include a Global Positioning System (GPS) receiver,componentry to perform triangulation (e.g., using beacons and/or otherfixed communication points), or other sensors to determine the relativelocation of fall protection equipment 11. An altimeter may be configuredto generate data indicative of an altitude of fall protection equipment11 above a fixed level. In some examples, the altimeter may beconfigured to determine altitude of fall protection equipment 11 basedon a measurement of atmospheric pressure (e.g., the greater thealtitude, the lower the pressure). In addition, status and environmentsensors 110 may include one or more sensors configured to measure windspeed, temperature, humidity, particulate content, noise levels, airquality, or any variety of other characteristics of environments inwhich fall protection equipment 11 may be used.

Output unit 112 may be configured to output data that is indicative ofoperation of fall protection equipment 11, e.g., as measured by one ormore sensors of computing device 98. In some examples, output unit 112may directly output the data from the sensors of computing device 98.For example, output unit 112 may generate one or more messagescontaining real-time or near real-time data from one or more sensors ofcomputing device 98 for transmission to another device via communicationunit 104. However, in some instances, communication unit 104 may not beable to communicate with such devices, e.g., due to an environment inwhich fall protection equipment 11 is located and/or network outages. Insuch instances, output unit 112 may cache usage data to memory 102. Thatis, output unit 112 (or the sensors themselves) may store usage data tomemory 102, which may allow the usage data to be uploaded to anotherdevice upon a network connection becoming available.

Output unit 112 may also be configured to generate an audible, visual,tactile, or other output that is perceptible by a user of fallprotection equipment 11. For example, output unit 112 may include onemore user interface devices including, as examples, a variety of lights,displays, haptic feedback generators, speakers or the like. In oneexample, output unit 112 may include one or more light emitting diodes(LEDs) that are located on fall protection equipment 11 and/or includedin a remote device that is in a field of view of a user of fallprotection equipment 11 (e.g., indicator glasses, visor, or the like).In another example, output unit 112 may include one or more speakersthat are located on fall protection equipment 11 and/or included in aremote device (e.g., earpiece, headset, or the like). In still anotherexample, output unit 112 may include a haptic feedback generator thatgenerates a vibration or other tactile feedback and that is included onfall protection equipment 11 or a remote device (e.g., a bracelet, ahelmet, an earpiece, or the like). In still another example, output unit112 may generate an electronic message for transmission to anothercomputing device, such as end-user computing devices 16, computingdevices 18, safety stations 15, hubs 14 (FIG. 1) or any other computingdevice.

In operation, fall protection unit 108 (or another computing devicecapable of communicating with computing device 98) may use data fromconnection sensors 106 to determine whether fall protection equipment 11is connected to a support structure. For example, fall protection unit108 may receive data from connections sensors 106 that indicates astatus or an operation of components of fall protection equipment 11.Fall protection unit 108 may determine a connection status of aplurality of articles of fall protection equipment 11 based on thereceived data. For example, fall protection unit 108 may determine thata particular article of fall protection equipment 11 is connected to asupport structure based on data indicating that components of fallprotection equipment 11 have been moved to allow connection to thesupport structure and that the support structure is disposed within anarea of attachment of fall protection equipment 11.

In some instances, fall protection unit 108 may control the operation oflock 109 and/or feedback component 113 based on the determinedconnection status. For example, based on determining that a particulararticle of fall protection equipment 11 is the only fall protectionequipment 11 that is connected to the support structure (e.g., accordingto the determined connection status), fall protection unit 108 mayactuate lock 109 in order to impede or prevent fall protection equipment11 from being disconnected from the support structure.

In some examples, lock 109 may be a secondary or tertiary lock of fallprotection equipment 11. For example, certain safety standards or codesmay require at least two separate and deliberate actions for componentsof fall protection equipment 11 to move (e.g., for a gate to move),thereby allowing fall protection equipment 11 to connect to ordisconnect from a support structure. As described in greater detailbelow with respect to FIGS. 4 and 5, each separate and deliberate actionmay be associated with a locking mechanism. According to aspects of thisdisclosure, lock 109 may prevent one or more of such locking mechanismsfrom being operated, e.g., from being opened to allow disconnection fromthe support structure. Fall protection unit 108 may also release lock109. For example, after actuating lock 109, fall protection unit 108 maycontinue to monitor whether fall protection equipment 11 is connected tothe support structure. In the event that one or more other articles offall protection equipment 11 are connected to the support structure,fall protection unit 108 may release lock 109 such that lock 109 nolonger impedes fall protection equipment 11 from being disconnected fromthe support structure.

In the event that fall protection unit 108 actuates lock 109, outputunit 112 may generate a signal that indicates lock 109 has beenactuated. For example, as described above, output unit 112 may generatean audible, visual, and/or tactile output that indicates lock 109 hasbeen actuated. In some examples, output unit 112 may additionally oralternatively generate an electronic message that indicates lock 109 hasbeen actuated for transmission to another computing device, such asend-user computing devices 16, computing devices 18, safety stations 15,hubs 14 (FIG. 1) or any other computing device.

In some instances, lock 109 may incorporate a manual override. Forexample, a user may manually perform one or more actions to release lock109 from a locked position to an unlocked position. In addition to orinstead of the alerts described above, output unit 112 may generate asignal that indicates lock 109 has been manually overridden by a user offall protection equipment 11. For example, output unit 112 may generatean electronic message, an audible output, a visual output, and/ortactile output that indicates a manual override has been performed.

In some examples, rather than actuating lock 109 (or in addition toactuating lock 109), fall protection unit 108 may actuate feedbackcomponent 113 based on the determined connection status. For example,based on determining that a particular article of fall protectionequipment 11 is the only fall protection equipment 11 that is connectedto the support structure (e.g., according to the determined connectionstatus), fall protection unit 108 may generate alert data and transmitthe alert data to feedback component 113. Upon receiving the alert data,fall protection equipment 11 may generate an alert that indicates thatthe first article of fall protection equipment is the only article offall protection equipment that is connected to the at least one supportstructure. That is, in some examples, feedback component 113 maygenerate an audible alert (e.g., via one or more speakers), a visualalert (e.g., via one or more displays, light emitting diodes (LEDs) orthe like), or a tactile alert (e.g., via a component of fall protectionequipment 11 that vibrates or provides other haptic feedback). In otherexamples, as noted above, output unit 112 may generate an electronicmessage that indicates the connection status, e.g., for transmission toanother device such as computing devices 18 (FIG. 1). In some examples,according to aspects of this disclosure, fall protection unit 108 maydetermine whether a fall has occurred. For example, fall protection unit108 may receive data from connection sensors 106 that indicates a loadbeing applied to fall protection equipment 11. In response to the loadexceeding a predetermined threshold, fall protection unit 108 maygenerate an audible, visual or tactile alert for output by output unit112. In some examples, fall protection unit 108 may also determine aduration with which the load is applied, e.g., to determine not onlythat a user has fallen (thereby generating the load), but is alsosuspended post fall.

FIG. 4 illustrates an example of a snap hook 120 that is configured inaccordance with aspects of this disclosure. While the exampleillustrated in FIG. 4 comprises a snap hook, it should be understoodthat the techniques described herein may be applied to a variety ofother devices for securing a user to an anchor, such as a carabiner. Forexample, a carabiner may be constructed similarly to snap hook 120, butmay rely on a rotating or self-locking gate mechanism instead of theplanar lock mechanism shown in FIG. 4.

The example snap hook 120 of FIG. 4 includes a movable gate 122 and abody 124 that generally defines an area of attachment 126 within which asupport structure is disposed when snap hook 120 is connected to thesupport structure. Snap hook 120 also includes first sensor 128 havingsensor elements 130, second sensor 132, computing device 134, primarylocking mechanism 136, and lock 138. Snap hook 120 may be attached to,for example, an energy absorbing lanyard, a self-retracting lanyard, oranother device via attachment point 140.

Movable gate 122 moves between an open position and a closed position.The example of FIG. 4 illustrates movable gate 122 in the closedposition such that movable gate 122 contacts body 120 and creates acontinuous loop that defines area of attachment 126. In the openposition, movable gate 122 pivots inward toward area of attachment 126and allows a support structure to be moved into area of attachment 126.

First sensor 128 may be configured to generate data that indicateswhether a material (such as a support structure) is disposed within areaof attachment 126. In the illustrated example, first sensor 128 includeselements 130 that outputs a signal in response to a magnetic field. Inthis example, first sensor 128 may generate data that indicates whethera ferrous material is disposed within area of attachment 126.

In an example for purposes of illustration, first sensor 128 may includea printed circuit board and elements 130 may include Hall Effectelements that are incorporated in the printed circuit board. In someinstances, permanent magnets may be positioned at the relative ends offirst sensor 128. When a ferrous object is in proximity to body 122,magnetic field lines change shape due to the tendency of electromagneticfields to be attracted to permeable objects. This change in the magneticfield results in a change in magnetic flux that is measured using theHall Effect elements.

In other examples, first sensor 128 may include a variety of othercontact or non-contact sensors. For example, first sensor 128 mayinclude any combination of reed switches, inductive sensors, ultrasonicsensors, photoelectric sensors, mechanical sensors, switches, or anyother sensor capable of generating an output based on a material beingdisposed within area of attachment 126.

Second sensor 132 may be configured to generate data that indicatesmovement of gate 122. For example, second sensor 132 may be configuredto generate a signal that indicates that gate 122 has been moved fromthe closed position to the open position or vice versa. In someexamples, second sensor 132 may output a discrete signal (e.g., a signalthat indicates whether gate 122 is in the open position or closedposition). In other examples, second sensor 132 may output dataindicative of a relative position of gate 122. Second sensor 132 mayinclude any sensor capable of generating an output based on a positionor movement of gate 122, such as one or more switches, rotary encoders,accelerometers, or the like.

Computing device 134 may include computing components responsible forprocessing and/or transmitting data generated by first sensor 128 andsecond sensor 132. Computing device 134 may also include a power source,such as a battery. In some examples, computing device 134 may beconfigured to include the components of computing device 98 shown inFIG. 3. In other examples, computing device 134 may include a subset ofcomputing device 98. For example, computing device 134 may simplyinclude one or more processors and a communication unit for transmittingdata from first sensor 128 and second sensor 132 to another computingdevice.

Primary locking mechanism 136 is configured to prevent gate 122 frombeing moved to the open position. For example, primary locking mechanism136 includes a component that engages with gate 122 to prevent gate 122from pivoting toward area of attachment 126. When a user operatesprimary locking mechanism 136 (e.g., a user squeezes primary lockingmechanism 136) the component of primary locking mechanism 136 disengagesfrom gate 122 to allow gate to be moved toward area of attachment 126.

According to aspects of this disclosure, lock 138 may be configured toimpede or prevent gate 122 from being moved from a closed position to anopen position based on a connection status of snap hook 120, therebyimpeding or preventing snap hook 120 from being disconnected from asupport structure. For example, computing device 134 (and/or anothercomputing device in communication with snap hook 120) may determinewhether snap hook 120 is connected to a support structure based on datafrom first sensor 128. That is, computing device 134 may receive datafrom first sensor 128 that indicates that a support structure is presentwithin area of attachment 126. Computing device 134 may determine aconnection status based on such data. For example, computing device 134may determine that snap hook 120 is connected when the support structureis present and disconnected when the support structure is not present.

In some examples, computing device 134 may also or alternatively usedata from second sensor 132 to determine the connection status. Forexample, computing device 132 may determine that snap hook 120 has beenconnected to a support structure based on a number of orderedoperations. In this example, computing device 134 may receive data fromsecond sensor 132 that indicates that gate 122 has moved to an openposition. Computing device 134 may the receive data from first sensor128 indicating that a support structure is disposed within area ofattachment 126. Computing device 134 may then receive data from secondsensor 132 that indicates that gate 122 has moved to a closed positionand determine that snap hook 120 has been connected to the supportstructure.

Computing device 134 may operate first sensor 128 based on data fromsecond sensor 132. For example, upon receiving data from second sensor132 that gate 122 has moved to an open position, computing device 134may activate first sensor 128 in order to identify a support structurewithin area of attachment 126.

After determining that snap hook 120 has been connected to a supportstructure, computing device 134 (or another computing device incommunication with snap hook 120) may monitor the status of one or moreother articles of fall protection equipment being used by the same user(referred to herein as a set of fall protection equipment). For example,computing device 134 may identify when the other articles of fallprotection equipment are connected to and disconnected from one or moresupport structure , e.g., as a worker moves throughout a worksite.Computing device 134 may determine when snap hook 120 is the onlyarticle of fall protection equipment in the set that is connected to thesupport structure. Based on this determination, computing device 134 mayactivate lock 138 in order to impede or prevent gate 122 from being tomoved from a closed position to an open position based on a connectionstatus of snap hook 120, thereby impeding or preventing snap hook 120from being disconnected from a support structure.

In some examples, lock 138 may include a locking component thatinterfaces directly with gate 122 in order to prevent gate 122 frombeing opened. For example, lock 138 may include a mechanical barrierthat prevents 122 from moving. In other examples, lock 138 may beconfigured to interface with one or more other locking mechanisms ofsnap hook 120, such as primary locking mechanism 136. For example, lock138 may include a mechanical barrier that prevents primary lockingmechanism 136 from moving, thereby preventing gate 122 from moving.

While the example described with respect to FIG. 4 includes primarylocking mechanism 136 and lock 138, other examples may includeadditional locking mechanisms. For example, certain safety standards orcodes may require at least two separate and deliberate actions for gate122 to open, thereby allowing snap hook 120 to connect to or disconnectfrom a support structure. Each separate and deliberate action may beassociated with a locking mechanism. Example locking mechanisms for snaphook 120 may include latches, spring loaded collars, levers, or anycombination of other components that require a deliberate action on thepart of the user to operate. According to aspects of this disclosure,lock 138 may be a tertiary locking mechanism that is included inaddition to the locking mechanisms associated with the two separate anddeliberate actions.

Computing device 134 may also release lock 138. For example, computingdevice 134 may continue to monitor whether fall protection equipment inthe set is connected to the support structure. In the event that one ormore other articles of fall protection equipment are connected to thesupport structure, computing device 134 may release lock 138 such thatlock 138 no longer impedes snap hook 120 from being disconnected fromthe support structure. Additionally or alternatively, lock 138 mayinclude a manual override that allows a user to manually release lock138.

In the event that computing device 134 actuates lock 138, computingdevice 134 may generate a signal that indicates lock 138 has beenactuated and/or that lock 138 has been manually overridden. In someexamples, computing device 134 may generate an electronic message, anaudible output, a visual output, and/or tactile output that indicatesthat lock 138 has been activated and/or a manual override has beenperformed.

It should be understood that the architecture and arrangement of snaphook 120 illustrated in FIG. 4 is shown for exemplary purposes only. Inother examples, snap hook 120 may be configured in a variety of otherways having additional, fewer, or alternative components than thoseshown in FIG. 4. For example, as noted above, snap hook 120 may beconfigured to include only a subset of components, such as first sensor128, second sensor 132, and a communication unit for transmitting datato another computing device, such as one of hubs 14, for performingcertain processing functions.

In another example, snap hook 120 may include a feedback component forindicating a connection status of snap hook 120. For example, thefeedback component may comprise any variety of speakers, displays,lights, haptic feedback components, or the like to generate an audiblealert, a visual alert, or a tactile alert in response to determiningthat snap hook 120 is the only article of fall protection connected to asupport structure.

In still another example, snap hook 120 may include one or morecomponents for determining whether a fall has occurred, such as fallsensor 142. For example, according to aspects of this disclosure, fallsensor 142 may comprise a switch, sensor, or the like for determining afall condition. In one example, fall sensor 142 may determinedeflection, movement, or motion of attachment point 140 to which a lineconstituent is attached in response to a load. If the load exceeds apredetermined threshold, fall sensor 142 (which may include hall-effectsensors, mechanical switches, or the like) may determine relativemovement or a change in shape of attachment point 140.

In addition to generating a signal in the event that attachment point140 (or another component located near the lower portion of snap hook120) moves a predetermined amount in response to a given load, theposition can also be monitored via sensors for a duration of time toindicate that a specific load has not only been applied to the connectorbut also applied for a duration. Based on such data, snap hook 120 (orcomputing device 98) may determine that a user has fallen (therebygenerating the load), but is also suspended post fall.

Based on data from fall sensor 142, snap hook 120 (or another device,such as computing device 98) may generate one or more alerts. Forexample, upon determining that a fall has occurred, fall sensor 142 maygenerate an audible, visual, or wireless communication (e.g., electronicmessage) that indicates that the fall has occurred.

FIG. 5 illustrates an example of a carrier sleeve 160 that is configuredin accordance with aspects of this disclosure. The example carriersleeve 160 of FIG. 5 includes a movable gate 162 and a body 164 thatgenerally defines an area of attachment 166 within which a supportstructure is disposed when carrier sleeve 160 is connected to thesupport structure, e.g., a vertically disposed cable that runs througharea of attachment 166. Carrier sleeve 160 also to includes first sensor168 having sensor element 170, second sensor 172, computing device 174,primary locking mechanism 176, secondary locking mechanism 178 and lock180.

Movable gate 162 moves between an open position and a closed position.The example of FIG. 5 illustrates movable gate 162 in the closedposition such that movable gate 162 is positioned proximate to body 164such that area of attachment 166 is a closed space that prevents acarrier from moving into or out of area of attachment 166. In the openposition, movable gate 162 pivots toward body 164 and allows a supportstructure to be moved into area of attachment 166.

First sensor 168 may be configured to generate data that indicateswhether a material (such as a support structure) is disposed within areaof attachment 166. In the illustrated example, first sensor 168 includeselement 170 that is configured to contact a support structure withinarea of attachment 166. For example, first sensor 168 may be a contactswitch and may generate a signal in response to a support structurecoming into contact with element 170. In other examples, first sensor168 may include a variety of other contact or non-contact sensors. Forexample, first sensor 168 may include any combination of Hall Effectsensors, reed switches, inductive sensors, ultrasonic sensors,photoelectric sensors, mechanical sensors, switches, or any other sensorcapable of generating an output based on a material being disposedwithin area of attachment 166.

Second sensor 172 may be configured to generate data that indicatesmovement of gate 162. For example, second sensor 172 may be configuredto generate a signal that indicates that gate 162 has been moved fromthe closed position to the open position or vice versa. In someexamples, second sensor 172 may output a discrete signal (e.g., a signalthat indicates whether gate 162 is in the open position or closedposition). In other examples, second sensor 172 may output dataindicative of a relative position of gate 162. Second sensor 172 mayinclude any sensor capable of generating an output based on a positionor movement of gate 162, such as one or more switches, rotary encoders,accelerometers, or the like.

Computing device 174 may include computing components responsible forprocessing and/or transmitting data generated by first sensor 168 andsecond sensor 172. Computing device 174 may also include a power source,such as a battery. In some examples, computing device 174 may beconfigured to include the components of computing device 98 shown inFIG. 3. In other examples, computing device 174 may include a subset ofcomputing device 98. For example, computing device 174 may simplyinclude one or more processors and a communication unit for transmittingdata from first sensor 168 and second sensor 172 to another computingdevice.

Primary locking mechanism 176 is configured to prevent gate 162 frombeing moved to the open position. For example, primary locking mechanism176 includes a component that engages with gate 162 to prevent gate 162from moving to the open position. When a user operates primary lockingmechanism 176 (e.g., a user rotates or otherwise moves primary lockingmechanism 176) the component of primary locking mechanism 176 disengagesfrom gate 162.

Secondary locking mechanism 178 is also configured to prevent gate 162from being moved to the open position. For example, secondary lockingmechanism 178 includes a spring component that prevents gate 162 frommoving to the open position without a deliberate action by a user ofcarrier sleeve 160. When a user operates secondary locking mechanism 178(e.g., a user presses secondary locking mechanism 178 to bias thespring) gate 162 moves to provide access to area of attachment 166.

According to aspects of this disclosure, lock 180 may be configured toimpede or prevent gate 162 from being moved from a closed position to anopen position based on a connection status of carrier sleeve 160,thereby impeding or preventing carrier sleeve 160 from beingdisconnected from a support structure. For example, computing device 174(and/or another computing device in communication with carrier sleeve160) may determine whether carrier sleeve 160 is connected to a supportstructure based on data from first sensor 168. That is, computing device174 may receive data from first sensor 168 that indicates that a supportstructure is present within area of attachment 166. Computing device 174may determine a connection status based on such data. For example,computing device 174 may determine that carrier sleeve 160 is connectedwhen the support structure is present and disconnected when the supportstructure is not present.

In some examples, computing device 174 may also or alternatively usedata from second sensor 172 to determine the connection status. Forexample, computing device 172 may determine that carrier sleeve 160 hasbeen connected to a support structure based on a number of orderedoperations. In this example, computing device 174 may receive data fromsecond sensor 172 that indicates that gate 162 has moved to an openposition. Computing device 174 may the receive data from first sensor168 indicating that a support structure is disposed within area ofattachment 166. Computing device 174 may then receive data from secondsensor 172 that indicates that gate 162 has moved to a closed positionand determine that carrier sleeve 160 has been connected to the supportstructure.

After determining that carrier sleeve 160 has been connected to asupport structure, computing device 174 (or another computing device incommunication with carrier sleeve 160) may monitor the status of one ormore other articles of fall protection equipment being used by the sameuser (referred to herein as a set of fall protection equipment). Forexample, computing device 174 may identify when the other articles offall protection equipment (such as one or more carabiners 120 (FIG. 4))are connected to and disconnected from one or more support structure,e.g., as a worker moves throughout a worksite. Computing device 174 maydetermine when carrier sleeve 160 is the only article of fall protectionequipment in the set that is connected to the support structure. Basedon this determination, computing device 174 may activate lock 180 inorder to impede or prevent gate 162 from being moved from a closedposition to an open position based on a connection status of carriersleeve 160, thereby impeding or preventing carrier sleeve 160 from beingdisconnected from a support structure.

In some examples, as described with respect to the example of FIG. 6below, lock 180 may include a locking component that interfaces directlywith gate 162 in order to prevent gate 162 from being opened. Forexample, lock 180 may include a mechanical barrier that prevents 162from moving. In other examples, lock 180 may be configured to interfacewith one or more other locking mechanisms of carrier sleeve 160, such asprimary locking mechanism 176 or secondary locking mechanism 178. Forexample, lock 180 may include a mechanical barrier that prevents primarylocking mechanism 176 from being moved or rotated, thereby preventinggate 162 from moving.

In some examples, computing device 174 may also release lock 180. Forexample, computing device 174 may continue to monitor whether fallprotection equipment in the set is connected to the support structure.In the event that one or more other articles of fall protectionequipment are connected to the support structure, computing device 174may release lock 180 such that lock 180 no longer impedes carrier sleeve160 from being disconnected from the support structure. Additionally oralternatively, lock 180 may include a manual override that allows a userto manually release lock 180.

In the event that computing device 174 actuates lock 180, computingdevice 174 may generate a signal that indicates lock 180 has beenactuated and/or that lock 180 has been manually overridden. In someexamples, computing device 174 may generate an electronic message, anaudible output, a visual output, and/or tactile output that indicatesthat lock 180 has been activated and/or a manual override has beenperformed.

It should be understood that the architecture and arrangement of carriersleeve 160 illustrated in FIG. 5 is shown for exemplary purposes only.In other examples, carrier sleeve 160 may be configured in a variety ofother ways having additional, fewer, or alternative components thanthose shown in FIG. 5. For example, as noted above, carrier sleeve 160may be configured to include only a subset of components, such as firstsensor 168, second sensor 172, and a communication unit for transmittingdata to another computing device, such as one of hubs 14, for performingcertain processing functions.

In another example, carrier sleeve 160 may include a feedback componentfor indicating a connection status of carrier sleeve 160. For example,the feedback component may comprise any variety of speakers, displays,lights, haptic feedback components, or the like to generate an audiblealert, a visual alert, or a tactile alert in response to determiningthat carrier sleeve 160 is the only article of fall protection connectedto a support structure.

In still another example, carrier sleeve 160 may include one or morecomponents for determining whether a fall has occurred, such as fallsensor 182. For example, according to aspects of this disclosure, fallsensor 182 may comprise a switch, sensor, or the like for determining afall condition. In one example, fall sensor 182 may determinedeflection, movement, or motion of a component that attaches carriersleeve 160 to a user in response to a load. If the load exceeds apredetermined threshold, fall sensor 182 (which may include hall-effectsensors, mechanical switches, or the like) may determine relativemovement or a change in shape of the attachment component. In otherexamples, fall sensor 182 may be positioned anywhere on carrier sleeve160 that allows fall sensor 182 to determine a change in load to acomponent that attaches carrier sleeve 160 to a user.

In addition to generating a signal in the event that an attachmentcomponent moves a predetermined amount in response to a given load, theposition can also be monitored via sensors for a duration of time toindicate that a specific load has not only been applied to the connectorbut also applied for a duration. Based on such data, carrier sleeve 160(or computing device 98) may determine that a user has fallen (therebygenerating the load), but is also suspended post fall.

Based on data from fall sensor 182, carrier sleeve 160 (or anotherdevice, such as computing device 98) may generate one or more alerts.For example, upon determining that a fall has occurred, fall sensor 182may generate an audible, visual, or wireless communication (e.g.,electronic message) that indicates that the fall has occurred.

FIG. 6 illustrates an example carrier sleeve 160 in greater detail. Forexample, as described above, lock 180 may be configured to impede orprevent gate 162 from being moved from a closed position to an openposition based on a connection status of carrier sleeve 160, therebyimpeding or preventing carrier sleeve 160 from being disconnected from asupport structure. In the example of FIG. 6, lock 180 includes asolenoid 182 that moves a pin 184 from an extended position 186 to aretracted position 188 and vice versa.

For example, as described above with respect to FIG. 5, computing device174 may determine when carrier sleeve 160 is the only article of fallprotection equipment in the set that is connected to the supportstructure. Based on this determination, computing device 174 mayactivate lock 180. Upon activating lock 180, pin 184 may move fromretracted position 188 to extended position 186. When in extendedposition 186, pin 184 may prevent gate 162 from moving from a closedposition to an open position. In some examples, pin 184 may directlyinterface with gate 162 to prevent gate 162 from being opened. In otherexamples, pin 184 may interface with another component of carrier sleeve160 (such as primary locking mechanism 176 or secondary lockingmechanism 178) to prevent gate 162 from being opened.

In some examples, computing device 174 may also release lock 180. Forexample, computing device 174 may continue to monitor whether fallprotection equipment in the set is connected to the support structure.In the event that one or more other articles of fall protectionequipment are connected to the support structure, computing device 174may release lock 180 by sending a signal to solenoid 182 to move pin 184from extended position 186 to retracted position 188. Additionally oralternatively, lock 180 may include a manual override that allows a userto manually move pin 184 from extended position 186 to retractedposition 188.

FIG. 7 illustrates an example of one of hubs 14 in greater detail. Forexample, hub 14 includes one or more processors 200, memory 202 that maystore usage data 204, connection data 206, and alert data 208,communication unit 210, sensors 212, user interface 214, and remoteinterface 216. It should be understood that the architecture andarrangement of hub 14 illustrated in FIG. 7 is shown for exemplarypurposes only. In other examples, hub 14 may be configured in a varietyof other ways having additional, fewer, or alternative components thanthose shown in FIG. 7. For example, hub 14 may also include one or morebatteries, charging components, or the like not shown in FIG. 7. Inaddition, while shown as a wearable device in the example of FIG. 7, inother examples, hub 14 may be implemented as stand-alone device deployedin a particular environment.

In general, hub 14 may enable and facilitate communication between fallprotection equipment 11 (e.g., such as snap hook 120 or carrier sleeve160) and PPEMS 6. For example, fall protection equipment 11 as well asother PPEs for a respective worker may communicate with hub 14 viaBluetooth or other short range protocol, and hub 14 may communicate withPPEMs 6 via wireless communications, such as via 802.11 WiFi protocols,or the like. In some examples, as described in greater detail herein,hub 14 may also control one or more components of fall protectionequipment 11 (e.g., such as locks) based on connection data 206,generate and/or output alerts, or perform a variety of other functions.

Processors 200, in one example, are configured to implementfunctionality and/or process instructions for execution within hub 14.For example, processors 200 may be capable of processing instructionsstored by memory 202. Processors 200 may include, for example,microprocessors, digital signal processors (DSPs), application specificintegrated circuits (ASICs), field-programmable gate array (FPGAs), orequivalent discrete or integrated logic circuitry.

Memory 202 may include a computer-readable storage medium orcomputer-readable storage device. In some examples, memory 202 mayinclude one or more of a short-term memory or a long-term memory. Memory202 may include, for example, random access memories (RAM), dynamicrandom access memories (DRAM), static random access memories (SRAM),magnetic hard discs, optical discs, flash memories, or forms ofelectrically programmable memories (EPROM) or electrically erasable andprogrammable memories (EEPROM).

In some examples, memory 202 may store an operating system (not shown)or other application that controls the operation of components of hub14. For example, the operating system may facilitate the communicationof data from memory 202 to communication unit 210. In some examples,memory 202 is used to store program instructions for execution byprocessors 200. Memory 202 may also be configured to store informationwithin hub 14 during operation. In the example shown in FIG. 5, memory202 may store usage data 204, connection data 206, and/or alert data208, as described in greater detail below.

Hub 14 may use communication unit 210 to communicate with externaldevices via one or more wired or wireless connections. Communicationunit 210 may include various mixers, filters, amplifiers and othercomponents designed for signal modulation, as well as one or moreantennas and/or other components designed for transmitting and receivingdata. Communication unit 210 may send and receive data to othercomputing devices using any one or more suitable data communicationtechniques. Examples of such communication techniques may includeTCP/IP, Ethernet, Wi-Fi, Bluetooth, 4G, LTE, to name only a fewexamples. For example, communication unit 210 may communicate with fallprotection equipment 11 or other PPE via Bluetooth or other short rangeprotocol, and communication unit 210 may communicate with PPEMs 6 viawireless communications, such as via 802.11 WiFi protocols, or the like.

Sensors 212 may include one or more sensors that generate dataindicative of an activity of a worker 10 associated with hub 14 and/ordata indicative of an environment in which hub 14 is located. Sensors212 may include, as examples, one or more accelerometers, one or more tosensors to detect conditions present in a particular environment (e.g.,sensors for measuring temperature, humidity, particulate content, noiselevels, air quality, or any variety of other characteristics ofenvironments in which fall protection equipment 11 may be used), or avariety of other sensors.

User interface 214 may include one more user interface devicesincluding, as examples, a variety of lights, displays, haptic feedbackgenerators, speakers or the like. In general, user interface 214 mayoutput a status of fall protection equipment 11 and/or hub 14, as wellas any alerts for worker 10. In one example, user interface 214 mayinclude a plurality of multi-color LEDs that illuminate to provideinformation to worker 10. In another example, user interface 214 mayinclude a motor that is configured to vibrate hub 14 to provide hapticfeedback to worker 10.

Remote interface 216 is configured to generate data for output atclients 62 (FIG. 2). For example, remote interface 216 may generate dataindicative of a status of fall protection equipment 11 and/or hub 14.For example, remote interface 216 may generate data that indicateswhether fall protection equipment 11 is connected to hub 14 and/orinformation about components of fall protection equipment 11. That is,remote interface 216 may generate data indicative of, as examples,remaining service life of fall protection equipment 11, a status of abattery of fall protection equipment 11, a connection status of fallprotection equipment 11, whether fall protection equipment 11 is theonly fall protection equipment connected to a support structure, whethera user has performed a manual override of a lock of fall protectionequipment, whether maintenance or replacement of fall protectionequipment 11 is needed, or the like. Remote interface 216 mayadditionally or alternatively generate data that is indicative of anyalerts issued by hub 14.

According to aspects of this disclosure, hub 14 may store usage data 204from sensors of fall protection equipment 11. Usage data 204 generallyrefers to data that is indicative of the manner in which a user usesfall protection equipment 11 including, as examples, data that indicatesa relative position of a component of fall protection equipment 11, datathat is indicative of whether a support structure is disposed within anarea of attachment of fall protection equipment 11, or other operationsor characteristics of fall protection equipment 11.

As described herein, sensors of fall protection equipment 11 maygenerate data regarding operation of fall protection equipment 11 andtransmit the data in real-time or near real-time to hub 14. In someexamples, hub 14 may immediately relay usage data 204 to anothercomputing device, such as PPEMS 6, via communication unit 210. In otherexamples, memory 202 may store usage data 204 for some time prior touploading the data to another device. For example, in some instances,communication unit 210 may be able to communicate with fall protectionequipment 11 but may not have network connectivity, e.g., due to anenvironment in which fall protection equipment 11 is located and/ornetwork outages. In such instances, hub 14 may store usage data 204 tomemory 202, which may allow the usage data to be uploaded to anotherdevice upon a network connection becoming available.

According to aspects of this disclosure, hub 14 also stores connectiondata 206 that indicates a connection status of one or more articles offall protection equipment 11 used by worker 10. That is, connection data206 may indicate whether respective articles of fall protectionequipment 11 in a set of fall protection equipment being used by worker10 are connected to a support structure. In some instances, hub 14 mayreceive connection data 206 from fall protection equipment 11, e.g., asdetermined by fall protection equipment 11. In other examples, hub 14may receive data from sensors of fall protection equipment 11 andprocessors 200 may determine connection data 206 based on the receivedsensor data.

According to aspects of this disclosure, hub 14 may control theoperation of fall protection equipment 11 based on connection data 206.For example, hub 14 may determine, based on connection data 206, thatfall protection equipment 11 has been connected to a support structure.Hub 14 may also determine when one or more articles of fall protectionequipment 11 have been disconnected from a support structure. Hub 14 maydetermine when a particular article of fall protection equipment 11 isthe only article of fall protection equipment 11 in a set that isconnected to a support structure. Based on this determination, in someexamples, hub 14 may issue an audible, visual, or tactile alert (e.g.,via user interface 214) or transmit an electronic message (e.g., viaremote interface 216) that indicates that fall protection equipment 11is the only article of fall protection equipment connected to thesupport structure. In other examples, hub 14 may activate a lock of fallprotection equipment in order to impede or prevent fall protectionequipment from being disconnected from the support structure.

According to aspects of this disclosure, hub 14 may store alert data 208for generating alerts for output by user interface 214 and/or remoteinterface 216. For example, hub 14 may receive alert data from PPEMS 6,fall protection equipment 11, end-user computing devices 16, remoteusers using computing devices 18, safety stations 15, or other computingdevices. In some examples, the alert data may be based on operation offall protection equipment 11. For example, hub 14 may receive alert data208 that indicates that fall protection equipment 11 is the only articleof fall protection equipment connected to the support structure. Asanother example, hub 14 may receive alert data 208 that indicatesoperation of a lock and/or that a lock has been manually overridden. Asstill another example, hub 14 may receive alert data 208 that indicatesthat a fall has occurred.

Hub 14 may interpret the received alert data 208 and generate an outputat user interface 214 (e.g., an audible, visual, or tactile output) orremote interface 216 to notify worker 10 or a remote party of the alertcondition (e.g., an operation or override of a lock, that theenvironment is dangerous, that fall protection equipment 11 ismalfunctioning, that one or more components of fall protection equipment11 need to be repaired or replaced, or the like). In some instances, hub14 may also interpret alert data 208 and issue one or more commands tofall protection equipment 11 to modify operation or enforce rules offall protection equipment 11 in order to bring operation of fallprotection equipment 11 into compliance with desired/less riskybehavior.

In general, while certain techniques or functions are described hereinas being performed by certain components, e.g., PPEMS 6, fall protectionequipment 11, or hubs 14, it should be understood that the techniques ofthis disclosure are not limited in this way. That is, certain techniquesdescribed herein may be performed by one or more of the components ofthe described systems. For example, in some instances, fall protectionequipment 11 may have a relatively limited sensor set and/or processingpower. In such instances, one of hubs 14 and/or PPEMS 6 may responsiblefor most or all of the processing of usage data, determining connectionstatus, and the like. In other examples, fall protection equipment 11may have additional sensors, additional processing power, and/oradditional memory, allowing for fall protection equipment 11 to performadditional techniques. Determinations regarding which components areresponsible for performing techniques may be based, for example, onprocessing costs, financial costs, power consumption, or the like.

FIG. 8 is a flow diagram illustrating an example process for controllingthe operation of an article of fall protection equipment, according toaspects of this disclosure. While the techniques shown in FIG. 8 aredescribed with respect to fall protection equipment 11, it should beunderstood that the techniques may be performed by a variety ofcomputing devices, such as one of hubs 14, PPEMS 6, or another computingdevice.

In the illustrated example, fall protection equipment 11 may determinethat fall protection equipment is connected to a support structure 11(220). For example, fall protection equipment may receive data from oneor more sensors incorporated in fall protection equipment 11 anddetermine a connection status based on the received data. In someinstances, received data may indicate that a support structure isdisposed within an area of attachment of fall protection equipment 11.In other instances, received data may indicate an operation of fallprotection equipment 11, such as the opening or closing of a gate offall protection equipment 11.

Fall protection equipment 11 may determine that fall protectionequipment 11 is the only fall protection equipment connected to asupport structure (222). For example, a worker may typically usemultiple articles of fall protection equipment (referred to herein as aset of fall protection equipment) to allow the worker to maintain atleast one connection to a support structure while the worker movesthroughout a worksite. That is, the worker may maintain at least oneconnection to a support structure when the worker disconnects from onesupport structure and connects to another support structure. Accordingto aspects of this disclosure, fall protection equipment 11 maydetermine that fall protection equipment 11 is the only fall protectionequipment in the set connected to a support structure.

Based on the determination, fall protection equipment 11 may perform atleast one operation. For example, according to aspects of thisdisclosure, fall protection equipment 11 may generate an alert thatindicates that the first article of fall protection equipment is theonly article of fall protection equipment that is connected to the atleast one support structure. That is, in some examples, fall protectionequipment 11 may generate an audible alert (e.g., via one or morespeakers), a visual alert (e.g., via one or more displays, lightemitting diodes (LEDs) or the like), or a tactile alert (e.g., via acomponent of fall protection equipment 11 that vibrates or providesother haptic feedback). In other examples, fall protection equipment 11may generate an electronic message, e.g., for transmission to anotherdevice such as computing devices 18 (FIG. 1).

Additionally or alternatively, to perform the at least one operation,fall protection equipment 11 may actuate a lock in order to impede orprevent fall protection equipment 11 from being disconnected from thesupport structure (224). In some instances, the lock may be a tertiarylock mechanism that may be overridden by perform a particular action orset of actions.

It is to be recognized that depending on the example, certain acts orevents of any of the techniques described herein can be performed in adifferent sequence, may be added, merged, or left out altogether (e.g.,not all described acts or events are necessary for the practice of thetechniques). Moreover, in certain examples, acts or events may beperformed concurrently, e.g., through multi-threaded processing,interrupt processing, or multiple processors, rather than sequentially.

In one or more examples, the functions described may be implemented inhardware, software, firmware, or any combination thereof. If implementedin software, the functions may be stored on or transmitted over acomputer-readable medium as one or more instructions or code, andexecuted by a hardware-based processing unit. Computer-readable mediamay include computer-readable storage media, which corresponds to atangible medium such as data storage media, or communication mediaincluding any medium that facilitates transfer of a computer programfrom one place to another, e.g., according to a communication protocol.In this manner, computer-readable media generally may correspond to (1)tangible computer-readable storage media which is non-transitory or (2)a communication medium such as a signal or carrier wave. Data storagemedia may be any available media that can be accessed by one or morecomputers or one or more processors to retrieve instructions, codeand/or data structures for implementation of the techniques described inthis disclosure. A computer program product may include acomputer-readable medium.

By way of example, and not limitation, such computer-readable storagemedia can comprise RAM, ROM, EEPROM, CD-ROM or other optical diskstorage, magnetic disk storage, or other magnetic storage devices, flashmemory, or any other medium that can be used to store desired programcode in the form of instructions or data structures and that can beaccessed by a computer. Also, any connection is properly termed acomputer-readable medium. For example, if instructions are transmittedfrom a website, server, or other remote source using a coaxial cable,fiber optic cable, twisted pair, digital subscriber line (DSL), orwireless technologies such as infrared, radio, and microwave, then thecoaxial cable, fiber optic cable, twisted pair, DSL, or wirelesstechnologies such as infrared, radio, and microwave are included in thedefinition of medium.

It should be understood, however, that computer-readable storage mediaand data storage media do not include connections, carrier waves,signals, or other transitory media, but are instead directed tonon-transitory, tangible storage media. Disk and disc, as used herein,includes compact disc (CD), laser disc, optical disc, digital versatiledisc (DVD), floppy disk and Blu-ray disc, where disks usually reproducedata magnetically, while discs reproduce data optically with lasers.Combinations of the above should also be included within the scope ofcomputer-readable media.

Instructions may be executed by one or more processors, such as one ormore digital signal processors (DSPs), general purpose microprocessors,application specific integrated circuits (ASICs), field programmablegate arrays (FPGAs), or other equivalent integrated or discrete logiccircuitry, as well as any combination of such components. Accordingly,the term “processor,” as used herein may refer to any of the foregoingstructures or any other structure suitable for implementation of thetechniques described herein. In addition, in some aspects, thefunctionality described herein may be provided within dedicated hardwareand/or software modules. Also, the techniques could be fully implementedin one or more circuits or logic elements.

The techniques of this disclosure may be implemented in a wide varietyof devices or apparatuses, including a wireless communication device orwireless handset, a microprocessor, an integrated circuit (IC) or a setof ICs (e.g., a chip set). Various components, modules, or units aredescribed in this disclosure to emphasize functional aspects of devicesconfigured to perform the disclosed techniques, but do not necessarilyrequire realization by different hardware units. Rather, as describedabove, various units may be combined in a hardware unit or provided by acollection of interoperative hardware units, including one or moreprocessors as described above, in conjunction with suitable softwareand/or firmware.

Various examples have been described. These and other examples arewithin the scope of the following claims.

1. A method comprising: determining that a first article of fallprotection equipment is connected to at least one support structure, thefirst article of fall protection equipment being included in a set offall protection equipment that comprises at least one second article offall protection equipment; determining that the first article of fallprotection equipment is the only article of fall protection equipment inthe set of fall protection equipment that is connected to the at leastone support structure; and performing, based on determining that thefirst article of fall protection equipment is the only article of fallprotection equipment that is connected to the at least one supportstructure, at least one operation.
 2. The method of claim 1, whereinperforming the at least one operation comprises generating an alert thatindicates that the first article of fall protection equipment is theonly article of fall protection equipment that is connected to the atleast one support structure. 3-4. (canceled)
 5. The method of claim 1,wherein performing the at least one operation comprises actuating a lockof the first article of fall protection equipment to impede the firstarticle of fall protection equipment from being disconnected from the atleast one support structure. 6-12. (canceled)
 13. The method of claim 1,further comprising: prior to determining that the first article of fallprotection equipment is the only article of fall protection equipmentthat is connected, determining that the at least one second article offall protection equipment is connected to the at least one supportstructure; determining that the at least one second article of fallprotection equipment is disconnected from the at least one supportstructure; and wherein determining that the first article of fallprotection equipment is the only article of fall protection equipmentthat is connected to the at least one support structure is responsive todetermining that the at least one second article of fall protectionequipment is disconnected from the at least one support structure. 14.The method of claim 1, wherein determining that the first article offall protection equipment is connected to the at least one supportstructure comprises: determining that a gate of the first article offall protection has opened; determining that the at least one supportstructure is disposed within an area of attachment of the first articleof fall protection equipment; and determining that the gate of the firstarticle of fall protection equipment has closed.
 15. (canceled)
 16. Themethod of claim 1, wherein the first article of fall protectionequipment comprises a carabiner or snap hook.
 17. The method of claim 1,wherein the first article of fall protection equipment comprises acarrier sleeve configured to be attached to a carrier support structure.18. A device comprising: a memory configured to store data thatindicates whether a first article of fall protection equipment isconnected to at least one support structure; and one or more processorsconfigured to communicate with the memory and configured to: determine,based on the data, that the first article of fall protection equipmentis connected to the at least one support structure, the first article offall protection equipment being included in a set of fall protectionequipment that comprises at least one second article of fall protectionequipment; determine that the first article of fall protection equipmentis the only article of fall protection equipment in the set of fallprotection equipment that is connected to the at least one supportstructure; and perform, based on determining that the first article offall protection equipment is the only article of fall protectionequipment that is connected to the at least one support structure, atleast one operation.
 19. The device of claim 18, wherein to perform theat least one operation, the one or more processors are configured togenerate an alert that indicates that the first article of fallprotection equipment is the only article of fall protection equipmentthat is connected to the at least one support structure. 20-21.(canceled)
 22. The device of claim 18, wherein to perform the at leastone operation, the one or more processors are configured to actuate,based on determining that the first article of fall protection equipmentis the only article of fall protection equipment that is connected tothe at least one support structure, a lock of the first article of fallprotection equipment to impede the first article of fall protectionequipment from being disconnected from the at least one supportstructure. 23-26. (canceled)
 27. The device of claim 18, wherein todetermine that the first article of fall protection equipment isconnected to the at least one support structure, the one or moreprocessors are configured to: determine that a gate of the first articleof fall protection has opened; determine that the at least one supportstructure is disposed within an area of attachment of the first articleof fall protection equipment; and determine that the gate of the firstarticle of fall protection equipment has closed.
 28. A fall protectiondevice comprising: a body that at least partially defines an area ofattachment for attachment of the fall protection device to a supportstructure; a movable gate connected to the body and configured to movebetween an open position and a closed position, wherein the openposition provides access to the area of attachment for attachment of thefall protection device to the support structure and the closed positionprevents access to the area of attachment; a first sensor configured togenerate data that indicates whether the support structure is disposedwithin the area of attachment.
 29. The fall protection device of claim28, further comprising a second sensor configured to generate data thatindicates a movement of the movable gate.
 30. The fall protection deviceof claim 28, wherein the second sensor is connected to the movable gate,and wherein to generate the data that indicates movement, the secondsensor is configured to generate data that indicates a movement of themovable gate.
 31. The fall protection device of claim 28, wherein thefirst sensor comprises a non-contact sensor such that the first sensoris configured to generate the data that indicates whether the supportstructure is disposed within the area of attachment without contactingthe support structure.
 32. (canceled)
 33. The fall protection device ofclaim 28, wherein the fall protection device comprises a carabiner orsnap hook and wherein the movable gate is configured to contact the bodyin the closed position to create a continuous loop that defines the areaof attachment.
 34. The fall protection device of claim 28, wherein thefall protection device comprises a carrier sleeve, and wherein the bodyis configured to at least partially define an area of attachment forvertical attachment to a carrier support structure.
 35. (canceled) 36.The fall protection device of claim 28, further comprising: a lockhaving a locked position and an unlock position, wherein the lockedposition impedes the movable gate from moving to the open position; andone or more processors configured to: determine that the fall protectiondevice is connected to the support structure, the fall protection devicebeing included in a set of fall protection equipment that comprises atleast one second article of fall protection equipment; determine thatthe fall protection device is the only article of fall protectionequipment in the set of fall protection equipment that is connected tothe support structure; and actuate, based on determining that the fallprotection device is the only article of fall protection equipment thatis connected to the support structure, the lock such that the lock is inthe locked position.
 37. (canceled)
 38. A system comprising: a set offall protection equipment comprising a first article of fall protectionequipment configured to be connected to at least one support structureand at least one second article of fall protection equipment configuredto be connected to the at least one support structure; a hub comprising:a communication unit configured to wirelessly communicate with the firstarticle of fall protection equipment and the at least one second articleof fall protection equipment; and one or more processors configured to:determine that the first article of fall protection equipment isconnected to the at least one support structure; determine that thefirst article of fall protection equipment is the only article of fallprotection equipment in the set of fall protection equipment that isconnected to the at least one support structure; and actuate, based ondetermining that the first article of fall protection equipment is theonly article of fall protection equipment that is connected to the atleast one support structure, a lock of the first article of fallprotection equipment to impede the first article of fall protectionequipment from being disconnected from the at least one supportstructure.
 39. The method of claim 1, further comprising: determining,for a user of the first article of fall protection equipment, that afall has occurred; and generating, based on determining that the fallhas occurred, an alert.